Skip to content

Overture website update - #53

Open
MitchellShiell wants to merge 57 commits into
mainfrom
overtureWebsiteUpdate
Open

Overture website update#53
MitchellShiell wants to merge 57 commits into
mainfrom
overtureWebsiteUpdate

Conversation

@MitchellShiell

@MitchellShiell MitchellShiell commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

What this does

Splits this repository into two builds so that overture.bio serves the marketing site with its home page at /, and docs.overture.bio keeps serving the documentation. The whole code side is here. What remains is Netlify and DNS work, written out below.

docusaurus.config.ts now reads OVERTURE_SITE:

docs.overture.bio overture.bio
Command npm run build npm run build:marketing
Output website/build website/build-marketing
OVERTURE_SITE unset marketing
Routes documentation only marketing only, home at /

Unset is the documentation site, so nothing about the current build changes unless someone opts in. Locally, npm start and npm run start:marketing run them; both default to port 3000, so pass -- --port 3001 to run them side by side.

Netlify Updates

Update the overture.bio site on netlify

New site from Git, overture-stack/docs, the same branch the documentation site builds:

  • Base directory: website
  • Build command: npm ci && npm run build:marketing
  • Publish directory: website/build-marketing
  • Environment variables: OVERTURE_SITE = marketing, and NODE_VERSION = 20 or 22, either works

Matomo site ID

Please ensure we are not breaking anything re matomo tracking

Resolves PR #911's conflict against origin/develop. 18 develop commits
absorbed; the single two-sided edit, the support link in
docs/02-Reference/00-submitting-metadata.md, keeps this branch's rewrite
over develop's stale docs.overture.bio path. Develop's own additions are
intact: the -ad allow-duplicates flag, the JetBrains README logo, and the
repo-wide formatter pass.
Resolves PR #504's conflict against origin/develop. 6 develop commits
absorbed across four conflicts: two support/reference-link rewrites kept
over develop's stale docs.overture.bio paths, README.md combined with
develop's Environment typo fix, and the Makefile Compose detection kept as
this branch's probe-with-fallback in place of develop's hardcoded
$(shell which docker) compose.

Develop's score -> score-client image rename, --remove-orphans, and
JetBrains logo are all intact. The branch's removal of --validate from the
upload options table still holds: #503 adds no CLI flag, and --validate is
declared only on DownloadCommand.
PR #257 was BEHIND by one commit (8195c9a, next@^12 vulnerability
upgrade). Rebased onto origin/main rather than taking GitHub's offered
merge commit, for consistency with the song and score rebases and to keep
history linear. No conflicts: that commit touches only package.json and
package-lock.json, while the branch touches docs/ and dev-services/.
Resolves PR #448's conflict against origin/main. 43 main commits
absorbed, one conflict: README.md, where main and this branch had
independently repointed the same stale under-development/lectern link.
Main used the older docs/core-software scheme, so this branch's
/develop/Lectern/overview wins, matching the site rename already applied
across song and score.

Main's prettier reformat of docs/03-dictionaryReference.md and its
displayName additions survive untouched. The docs/04-viewer/ pages were
verified against the rebased packages/ui: entry points,
DictionaryTableProps, CustomColumnConfig and MetaValueRenderer all match.
PR #297 targets M5-revised, the TypeScript rewrite, not master. 83
commits absorbed from a 2023 merge base.

The Java maestro-app config and the five old doc pages stay deleted; the
replacement pages cover their content and are more accurate, since
M5-revised's tech.md and README still list the kafka and repository
packages that 2cad87c consolidated away, and its setup.md points at a
nonexistent .env.schema.

Two corrections on top of the rebase: the README still carried master's
Java 11 and Maven prerequisites, which would have regressed the
TypeScript branch, and both setup guides documented a make help target
that does not exist.
Resolves PR #1089's conflicts. 11 commits absorbed, four conflicts.

MCP tool names: main's #1088 renamed them to snake_case and this branch
still had kebab-case, so main wins, verified against apps/mcp-server/src.
docs/mcp-server.md combined, keeping main's new query_arranger Prompts
block from #1087 alongside this branch's heading promotion.

The two .dev conflicts follow the branch's own drop-.dev-changes intent,
so .dev matches main exactly, except tech-debt.md where both entries are
kept: they are additive, and this branch's OpenSearch entry explains why
its Makefile change removes the start-os target.
Closes the unclosed code fence in docs/03-dictionaryReference.md that
trapped the ## Field Restrictions heading inside a code block. Docusaurus
was failing the site build on two broken anchors pointing at it, one from
the Lectern page itself and one from
website/docs/use-docs/administration/01-building-dictionaries.mdx.
@netlify

netlify Bot commented Aug 11, 2026

Copy link
Copy Markdown

Deploy Preview for overturedocs canceled.

Name Link
🔨 Latest commit 5066906
🔍 Latest deploy log https://app.netlify.com/projects/overturedocs/deploys/6a84a7e8a900160008fa30c5

@MitchellShiell
MitchellShiell marked this pull request as ready for review August 18, 2026 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant